home *** CD-ROM | disk | FTP | other *** search
-
-
-
- llllbbbbooooooootttt((((1111MMMM)))) llllbbbbooooooootttt((((1111MMMM))))
-
-
-
- NNNNAAAAMMMMEEEE
- lboot - configure bootable kernel
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- llllbbbbooooooootttt _o_p_t_i_o_n_s
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- The _l_b_o_o_t command is used to configure a bootable UNIX kernel. Master
- files in the directory _m_a_s_t_e_r contain configuration information used by
- _l_b_o_o_t when creating a kernel. System files in the directory _s_y_s_t_e_m are
- used by _l_b_o_o_t to determine which modules are to be configured into the
- kernel.
-
- If a module in _m_a_s_t_e_r is specified in the _s_y_s_t_e_m file via "INCLUDE:",
- that module is included in the bootable kernel. For all included
- modules, _l_b_o_o_t searches the _b_o_o_t directory for an object file with the
- same name as the file in _m_a_s_t_e_r, but with a ....oooo or ....aaaa appended. If found,
- this object is included when building the bootable kernel.
-
- For every module in the _s_y_s_t_e_m file specified via "VECTOR:", _l_b_o_o_t takes
- actions to determine if a hardware device corresponding to the specified
- module exists. Generally, the action is a memory read at a specified
- base, of the specified size. If the read succeeds, the device is assumed
- to exist, and its module is also included in the bootable kernel.
-
- Master files that are specified in the _s_y_s_t_e_m file via "EXCLUDE:" are
- also examined; stubs are created for routines specified in the excluded
- master files that are not found in the included objects.
-
- Master files that are specified in the _s_y_s_t_e_m file via "USE:" are treated
- as though the file were specified via the "INCLUDE:" directive, if an
- object file corresponding to the master file is found in the _b_o_o_t
- directory. If no such object file is found, "USE:" is treated as
- "EXCLUDE:".
-
- To create the new bootable object file, the applicable master files are
- read and the configuration information is extracted and compiled. The
- output of this compilation is then linked with all included object files.
- Unless directed otherwise in the _s_y_s_t_e_m file, the information is compiled
- with $$$$TTTTOOOOOOOOLLLLRRRROOOOOOOOTTTT////uuuussssrrrr////bbbbiiiinnnn////cccccccc and combined with the modules in the _b_o_o_t
- directory using $$$$TTTTOOOOOOOOLLLLRRRROOOOOOOOTTTT////uuuussssrrrr////bbbbiiiinnnn////lllldddd.
-
- The options are:
-
- ----mmmm _m_a_s_t_e_r Specifies the directory containing the master files to be
- used for the bootable kernel. The default _m_a_s_t_e_r directory
- is $_R_O_O_T/_v_a_r/_s_y_s_g_e_n/_m_a_s_t_e_r._d.
-
- ----ssss _s_y_s_t_e_m Specifies the directory containing the system files. The
- default _s_y_s_t_e_m directory is $_R_O_O_T/_v_a_r/_s_y_s_g_e_n/_s_y_s_t_e_m.
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- llllbbbbooooooootttt((((1111MMMM)))) llllbbbbooooooootttt((((1111MMMM))))
-
-
-
- ----bbbb _b_o_o_t Specifies the directory where object files are to be found.
- The default _b_o_o_t directory is $_R_O_O_T/_v_a_r/_s_y_s_g_e_n/_b_o_o_t.
-
- ----nnnn _m_t_u_n_e Specifies the directory where tunable parameters are to be
- found. The default _m_t_u_n_e directory is
- $_R_O_O_T/_v_a_r/_s_y_s_g_e_n/_m_t_u_n_e.
-
- ----cccc _s_t_u_n_e Specifies the name of the file defining customized tunable
- parameter values. The default _s_t_u_n_e file is
- $_R_O_O_T/_v_a_r/_s_y_s_g_e_n/_s_t_u_n_e.
-
- ----rrrr _R_O_O_T RRRROOOOOOOOTTTT becomes the starting pathname when finding files of
- interest to _l_b_o_o_t. Note that this option sets RRRROOOOOOOOTTTT as the
- search path for include files used to generate the target
- kernel. If this option is not specified, the RRRROOOOOOOOTTTT
- environment variable (if any) is used instead.
-
- ----vvvv Makes _l_b_o_o_t slightly more verbose.
-
- ----uuuu _u_n_i_x Specifies the name of the target kernel. By default, it is
- uuuunnnniiiixxxx....nnnneeeewwww, unless the ----tttt option is used, in which case the
- default is uuuunnnniiiixxxx....iiiinnnnssssttttaaaallllllll.
-
- ----dddd Displays debugging information about the devices and modules
- put in the kernel.
-
- ----aaaa Used to auto-register all dynamically loadable kernel modules
- that contain a dddd and an RRRR in their master files. Only the
- auto-register is performed, a kernel is not configured.
-
- ----NNNN Disables auto-registering of all dynamically loadable
- modules. A kernel is produced, but no auto-registration is
- performed.
-
- ----llll Used to ignore the dddd in all master files and link all
- necessary modules into the kernel.
-
- ----eeee Causes the result of whether an auto-config would have been
- performed to be printed, but no actual configuration is
- built.
-
- ----wwww Used to specify a work directory into which the _m_a_s_t_e_r._c and
- _e_d_t._l_i_s_t files are written. By default these files are
- written into the _b_o_o_t directory.
-
- ----tttt Tests if the existing kernel is up-to-date. If the kernel is
- not up-to-date, it prompts you to proceed. It compares the
- modification dates of the _s_y_s_t_e_m files, the object files in
- the _b_o_o_t directory, the modification time of the boot
- directory, the configuration files in the _m_a_s_t_e_r._d directory
- and the modification time of the _s_t_u_n_e file with that of the
- existing kernel. It also probes for the devices specified
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-
-
-
- llllbbbbooooooootttt((((1111MMMM)))) llllbbbbooooooootttt((((1111MMMM))))
-
-
-
- with "VECTOR:" lines in the _s_y_s_t_e_m file. If the devices have
- been added or removed, or if the kernel is out-of-date, it
- builds a new kernel, adding ....iiiinnnnssssttttaaaallllllll to the target name.
-
- ----TTTT Performs the same function as the ----tttt option, but does not
- prompt you to proceed.
-
- ----OOOO _t_a_g_s Specifies tags to be used to select which tunable parameters
- to use as part of the the kernel build. Multiple ----OOOO options
- may be given.
-
- ----LLLL _m_a_s_t_e_r Specifies the name of the dynamically loadable kernel module
- to load into the running kernel. _m_a_s_t_e_r is the name of a
- master file in the $_R_O_O_T/_v_a_r/_s_y_s_g_e_n/_m_a_s_t_e_r._d directory.
-
- ----RRRR _m_a_s_t_e_r Specifies the name of the dynamically loadable kernel module
- to register. _m_a_s_t_e_r is the name of a master file in the
- $_R_O_O_T/_v_a_r/_s_y_s_g_e_n/_m_a_s_t_e_r._d directory.
-
- ----UUUU _i_d Used to unload a dynamically loadable kernel module. _i_d is
- found by using the _l_b_o_o_t -_V command.
-
- ----WWWW _i_d Used to unregister a dynamically loadable kernel module. _i_d
- is found by using the _l_b_o_o_t -_V command.
-
- ----VVVV Used to list all of the currently registered and loaded
- dynamically loadable kernel modules.
-
- It is best to reconfigure the kernel on a system with the _a_u_t_o_c_o_n_f_i_g
- command.
-
- EEEEXXXXAAAAMMMMPPPPLLLLEEEE
- _llll_bbbb_oooo_oooo_tttt _----_ssss _n_e_w_s_y_s_t_e_m
-
- Reads the file named _n_e_w_s_y_s_t_e_m to determine which objects should be
- configured into the bootable object.
-
- FFFFIIIILLLLEEEESSSS
- /var/sysgen/system
- /var/sysgen/master.d/*
- /var/sysgen/boot/*
- /var/sysgen/mtune/*
- /var/sysgen/stune
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- autoconfig(1M), setsym(1M), systune(1M), master(4), mload(4), mtune(4),
- stune(4), system(4).
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 3333
-
-
-
-